Mobility integration with fabric enabled network

ABSTRACT

Systems, methods and computer readable media for mobility integration with fabric-enabled networks are described. Some implementations can include a method comprising terminating, using one or more processors, an access tunnel at an edge switch of a fabric-enabled network, and establishing, using the one or more processors, a mobility tunnel with the edge switch. The method can also include mapping, using the one or more processors, a mobility network to a service identifier associated with the mobility network. The method can further include forwarding, using the one or more processors, traffic for the mobility network from the edge switch to another edge switch across the fabric enabled network, wherein the traffic includes the service identifier.

FIELD

Embodiments relate generally to computer networks and more particularlyto mobility integration with fabric enabled networks.

BACKGROUND

In some current mobility deployments within fabric based networks suchas shortest path bridging networks with MAC and MAC encapsulation accesspoints terminate access tunnels on wireless switching plane. Thewireless switching plane attaches to a fabric enabled network andestablishes a mobility tunnel with peer wireless switching planes overthe fabric enabled network.

Wireless switching planes advertise services to peer wireless switchingplanes over mobility tunnels. Mobility tunnels provide seamless mobilityby extending the client networks with the help of a signaling plane.Within the wireless switching planes, client traffic is encapsulatedusing a header and the fabric network may apply policies to theencapsulated frame. Mobility services offered using the fabric enablednetwork may include transport only (e.g., establishing mobility tunnelsover an SPBM network).

A need may exist for a signaling plane to extend a client networkwhenever a client roams. A fabric enabled network may need to applypolicies to encapsulated tunnel frames. When traffic is roaming acrossthe network, it may be required to traverse one extra hop through a VLANserver to reach the roaming client. Also, traffic disruption may occurduring the VLAN server fail over as the signaling plane has to reelect aVLAN server and reprogram the new VLAN server in the data path.

Embodiments were conceived in light of the above-mentioned problems andlimitations, among other things.

SUMMARY

Some implementations can include a method comprising terminating, usingone or more processors, an access tunnel at an edge switch of afabric-enabled network, and establishing, using the one or moreprocessors, a mobility tunnel with the edge switch. The method can alsoinclude mapping, using the one or more processors, a mobility network toa service identifier associated with the mobility network. The methodcan further include forwarding, using the one or more processors,traffic for the mobility network from the edge switch to another edgeswitch across the fabric enabled network, wherein the traffic includesthe service identifier.

The fabric-enabled network can include an SPBm network. The edge switchcan include a backbone edge bridge. The mobility tunnel can beestablished between a wireless switching plane component and the edgeswitch. The mobility network can be a mobility VLAN. The serviceidentifier can include an ISID.

The method can also include determining that a client device is roamingto a different access point. The method can further include dynamicallybinding the mobility network to a service identifier at a wirelessswitching plane component associated with the different access point.

Some implementations can include a system comprising one or moreprocessors configured to perform operations. The operations can includeterminating, using one or more processors, an access tunnel at an edgeswitch of a fabric-enabled network, and establishing, using the one ormore processors, a mobility tunnel with the edge switch. The operationscan also include interconnecting, using the one or more processors, themobility tunnel on the edge switch with another mobility tunnelassociated with a wireless switching plane component. The operations canfurther include mapping, using the one or more processors, a mobilitynetwork to a service identifier associated with the mobility network.The operations can also include exchanging, using the one or moreprocessors, traffic from the mobility tunnel associated with the edgeswitch with traffic from the other mobility tunnel associated with thewireless switching plane component.

The fabric-enabled network can include an SPBm network. The edge switchcan include a backbone edge bridge. The other mobility tunnel can beestablished between a wireless switching plane component and anon-fabric enabled network.

The mobility network can be a mobility VLAN. The service identifier canbe an ISID. The operations can also include determining that a clientdevice is roaming to a different access point. The operations canfurther include dynamically binding the mobility network to a serviceidentifier at a wireless switching plane component associated with thedifferent access point.

Some implementations can include a nontransitory computer readablemedium having stored thereon software instructions that, when executedby a processor, cause the processor to perform operations. Theoperations can include terminating, using one or more processors, anaccess tunnel at an edge switch of a fabric-enabled network. Theoperations can also include establishing, using the one or moreprocessors, a mobility tunnel with the edge switch. The operations canfurther include mapping, using the one or more processors, a mobilitynetwork to a service identifier associated with the mobility network.The operations can also include forwarding, using the one or moreprocessors, traffic for the mobility network from the edge switch toanother edge switch across the fabric enabled network, wherein thetraffic includes the service identifier.

The fabric-enabled network can include an SPBm network. The edge switchcan include a backbone edge bridge. The mobility tunnel can beestablished between a wireless switching plane component and the edgeswitch. The mobility network can be a mobility VLAN. The serviceidentifier can include an ISID.

The operations can also include determining that a client device isroaming to a different access point. The method can further includedynamically binding the mobility network to a service identifier at awireless switching plane component associated with the different accesspoint.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an example system for mobility integration withfabric enabled networks in accordance with at least one embodiment.

FIG. 2 is a flowchart of an example method for mobility integration withfabric enabled networks in accordance with at least one embodiment.

FIG. 3 is a diagram of an example system for mobility integration withfabric enabled networks in accordance with at least one embodiment.

FIG. 4 is a flowchart of an example method for mobility integration withfabric enabled networks in accordance with at least one embodiment.

FIG. 5 is a diagram of an example computer system for mobilityintegration with fabric enabled networks in accordance with at least oneembodiment.

DETAILED DESCRIPTION

FIG. 1 shows a diagram of an example network 100 including a wirelesscontrol plane 102, an SPBM network 104, a first backbone edge bridge(BEB) 106, a second backbone edge bridge 108, and a third backbone edgebridge 110. The network 100 also includes a wireless switching plane112, a first access point 114, a second access point 116, a third accesspoint 118, a fourth access point 120, a first client 122, a secondclient 124, and a third client 126.

In operation, the second client 124 may be accessing the network viaaccess point 114 but may be roaming and need to access the network viaaccess point 116. Access point 114 terminates an access tunnel frombackbone edge bridge 106 and access point 116 terminates an accesstunnel on backbone edge bridge 110.

Wireless switching plane 118 terminates mobility tunnel with a backboneedge bridge 106 and access point 118 terminates an access tunnel on thewireless switching plane 112. The backbone edge bridges 106 to 110 andthe wireless switching plane 112 can download mobility VLANs (e.g.“employee”, “HR” and “finance”) from the wireless control plane. Thebackbone edge bridge 106 and the backbone edge bridge 108 can provideservice for the “employee” VLAN. The backbone edge bridge 110 canprovide service for the “HR” VLAN, and the wireless switching plane 112can provide service for the “finance” VLAN. The backbone edge bridge 106and the backbone edge bridge 108 can map the MVLAN “employee” to ISID10, while the backbone edge bridge 110 can map the MVLAN “HR” to ISID20.

The client 122 and the client 124 can associate with access point 114and can be assigned to mobility VLAN “employee”. Access point 114 andbackbone edge bridge 106 can program the access tunnel “employee”.

In this example, the client 124 is roaming from access point 114 toaccess point 116. The access point 116 requests the backbone edge bridge110 to provide service in the MVLAN “employee”. The backbone edge bridge110 creates a dynamic binding between the MVLAN “employee” and ISID 10.The backbone edge bridge 110 sends a triggered update of the dynamicbinding to other peer BEBs. The peer BEBs record the information for thedynamic binding.

The backbone edge bridge 110 broadcasts GARPs on behalf of the client,on ISID 10 which is mapped to MVLAN “employee”. The backbone edge bridge106 and the backbone edge bridge 108 record the MAC movement. Thebackbone edge bridge 110 bridges the traffic destined to the client 122to backbone edge bridge 108 over the SPBM network 104.

The BEBs can delete the dynamic binding in response to a detectedcondition, such as inactivity from the roaming client. The fabricenabled network (e.g., SPBm network) can apply policies to the clienttraffic.

FIG. 2 shows an example flowchart method for mobility integration with afabric enabled network. Processing begins at 202, where an access tunnelis terminated at an edge which of a network. For example, an accesstunnel can be terminated at a backbone edge bridge of a SPBM network.The access tunnel connecting an access point with the backbone edgebridge. Processing continues to 204.

At 204, a mobility tunnel is established with the edge switch. Themobility tunnel can connect a wireless switching plane with the edgeswitch, for example, a BEB. Processing continues to 206.

At 206, a mobility network is mapped to a service identifier. Forexample, a MVLAN can be mapped to an ISID. Once the mapping is done,traffic for the mobility network can be forwarded from one edge switch(e.g., BEB) to another edge switch across the fabric enabled networkusing the service identifier, which can be included in the traffic.

It will be appreciated that steps 202 through 206 can be repeated inwhole or in part in order to accomplish a contemplated mobilityintegration task.

FIG. 3 shows a diagram of an example network for internet working offabric capable WSPs and/or BEBs with non-fabric capable WSPs. Inparticular, the network 300 includes a wireless control plane 302, afabric network 304, a first backbone edge bridge 306, a second backboneedge bridge 308, a first wireless switching plane 310, a second wirelessswitching plane 312, a first access point 314, a second access point316, a first client 318 and a second client 320.

In operation, the access point 314 terminates an access tunnel on thewireless switching plane 310 and the access point 316 terminates anaccess tunnel on the wireless switching plane 312. Wireless switchingplane 310 terminates a mobility tunnel with backbone edge bridge 306 andwireless switching plane 312 terminates a mobility tunnel with backboneedge bridge 308.

The backbone edge bridges and the wireless switching planes download themobility VLAN “employee”, “HR” and “finance” from the wireless controlplane 302. The backbone edge bridge 306 provides service for the“employee” MVLAN, the backbone edge bridge 308 provides service for the“HR” MVLAN, and the wireless switching plane 310 and wireless switchingplane 312 provides service for the “finance” MVLAN.

The backbone edge bridge 306 maps the MVLAN “employee” to ISID 10, thebackbone edge bridge 308 maps the MVLAN “HR” to ISID 20.

The client 318 and the client 320 associates with access point 314 andare assigned to the mobility VLAN “finance”. The access point 314 andthe wireless switching plane 310 program an access tunnel in the“finance” MVLAN.

The client 320 is roaming to access point 316. Access point 316 requestswireless switching plane 312 to provide service in the MVLAN “finance”.The wireless switching plane 312 in turn requests the backbone edgebridge 308 for service in the MVLAN “finance”. The backbone edge bridge308 creates a dynamic binding between MVLAN “finance” and ISID 10 (fromreserve range). The backbone edge bridge 308 sends a triggered update ofthe dynamic binding to the peer backbone edge bridges. The peer backboneedge bridges terminating the mobility tunnel will create a dynamicbinding between the MVLAN finance and the ISID 1000.

The backbone edge bridge 308 broadcasts GARPs messages on behalf of theclient on ISID 1000 which is mapped to MVLAN “finance”. Traffic flowsfrom client 320 to client 318 in the following path: client 320 toaccess point 316, to wireless switching plane 312, to backbone edgebridge 308, to backbone edge bridge 306, to wireless service 310, toaccess point 314, and finally to client 318.

FIG. 4 shows a flowchart of an example method for internet working offabric capable and non-fabric capable WSPs. Processing begins at 402where an access tunnel is terminated at an edge switch of a network.Processing continues to 404.

At 404, the mobility tunnel is established between a wireless switchingplane and an edge switch. Processing continues to 406.

At 406, the mobility network is mapped to a service identifier.Processing continues to 408.

At 408, the system determines if a client is roaming to a new accesspoint. Processing continues to 410.

At 410, a backbone edge bridge associated with the new access pointdynamically binds an MVLAN to a service identifier at the wirelessswitching plane associated with the new access point.

It will be appreciated that steps 402 to 410 can be repeated in whole orin part in order to accomplish a contemplated internet working task.

FIG. 5 is a diagram of an example computer system 500 in accordance withat least one implementation. The computer 500 includes a processor 502,operating system 504, memory 506 and I/O interface 508. The memory 506can include a mobility integration application 510 and a database 512.

In operation, the processor 502 may execute the application 410 storedin the memory 506. The application 510 can include software instructionsthat, when executed by the processor, cause the processor to performoperations for mobility integration in accordance with the presentdisclosure (e.g., performing one or more of steps 202-206 and/or402-410).

The application program 510 can operate in conjunction with the database512 and the operating system 504.

It will be appreciated that the modules, processes, systems, andsections described above can be implemented in hardware, hardwareprogrammed by software, software instructions stored on a nontransitorycomputer readable medium or a combination of the above. A system asdescribed above, for example, can include a processor configured toexecute a sequence of programmed instructions stored on a nontransitorycomputer readable medium. For example, the processor can include, butnot be limited to, a personal computer or workstation or other suchcomputing system that includes a processor, microprocessor,microcontroller device, or is comprised of control logic includingintegrated circuits such as, for example, an Application SpecificIntegrated Circuit (ASIC). The instructions can be compiled from sourcecode instructions provided in accordance with a programming languagesuch as Java, C, C++, C#.net, assembly or the like. The instructions canalso comprise code and data objects provided in accordance with, forexample, the Visual Basic™ language, or another structured orobject-oriented programming language. The sequence of programmedinstructions, or programmable logic device configuration software, anddata associated therewith can be stored in a nontransitorycomputer-readable medium such as a computer memory or storage devicewhich may be any suitable memory apparatus, such as, but not limited toROM, PROM, EEPROM, RAM, flash memory, disk drive and the like.

Furthermore, the modules, processes systems, and sections can beimplemented as a single processor or as a distributed processor.Further, it should be appreciated that the steps mentioned above may beperformed on a single or distributed processor (single and/ormulti-core, or cloud computing system). Also, the processes, systemcomponents, modules, and sub-modules described in the various figures ofand for embodiments above may be distributed across multiple computersor systems or may be co-located in a single processor or system. Examplestructural embodiment alternatives suitable for implementing themodules, sections, systems, means, or processes described herein areprovided below.

The modules, processors or systems described above can be implemented asa programmed general purpose computer, an electronic device programmedwith microcode, a hard-wired analog logic circuit, software stored on acomputer-readable medium or signal, an optical computing device, anetworked system of electronic and/or optical devices, a special purposecomputing device, an integrated circuit device, a semiconductor chip,and/or a software module or object stored on a computer-readable mediumor signal, for example.

Embodiments of the method and system (or their sub-components ormodules), may be implemented on a general-purpose computer, aspecial-purpose computer, a programmed microprocessor or microcontrollerand peripheral integrated circuit element, an ASIC or other integratedcircuit, a digital signal processor, a hardwired electronic or logiccircuit such as a discrete element circuit, a programmed logic circuitsuch as a PLD, PLA, FPGA, PAL, or the like. In general, any processorcapable of implementing the functions or steps described herein can beused to implement embodiments of the method, system, or a computerprogram product (software program stored on a nontransitory computerreadable medium).

Furthermore, embodiments of the disclosed method, system, and computerprogram product (or software instructions stored on a nontransitorycomputer readable medium) may be readily implemented, fully orpartially, in software using, for example, object or object-orientedsoftware development environments that provide portable source code thatcan be used on a variety of computer platforms. Alternatively,embodiments of the disclosed method, system, and computer programproduct can be implemented partially or fully in hardware using, forexample, standard logic circuits or a VLSI design. Other hardware orsoftware can be used to implement embodiments depending on the speedand/or efficiency requirements of the systems, the particular function,and/or particular software or hardware system, microprocessor, ormicrocomputer being utilized. Embodiments of the method, system, andcomputer program product can be implemented in hardware and/or softwareusing any known or later developed systems or structures, devices and/orsoftware by those of ordinary skill in the applicable art from thefunction description provided herein and with a general basic knowledgeof the software engineering and computer networking arts.

Moreover, embodiments of the disclosed method, system, and computerreadable media (or computer program product) can be implemented insoftware executed on a programmed general purpose computer, a specialpurpose computer, a microprocessor, a network server or switch, or thelike.

It is, therefore, apparent that there is provided, in accordance withthe various embodiments disclosed herein, methods, systems and computerreadable media for mobility integration with fabric enabled networks.

While the disclosed subject matter has been described in conjunctionwith a number of embodiments, it is evident that many alternatives,modifications and variations would be, or are, apparent to those ofordinary skill in the applicable arts. Accordingly, Applicants intend toembrace all such alternatives, modifications, equivalents and variationsthat are within the spirit and scope of the disclosed subject matter.

What is claimed is:
 1. A method comprising: terminating, using one ormore processors, an access tunnel at an edge switch of a fabric-enablednetwork, wherein the fabric enabled network includes a shortest pathbridging mac-in-mac encapsulation (SPBm) network; establishing, usingthe one or more processors, a mobility tunnel with the edge switch;mapping, using the one or more processors, a mobility VLAN network to aservice instance identifier (ISID) of the SPBm network so as toassociate the ISID with the mobility VLAN network; and forwarding, usingthe one or more processors, traffic for the mobility VLAN network fromthe edge switch to another edge switch across the fabric enabled networkaccording to an ISID value within the traffic.
 2. The method of claim 1,wherein the edge switch includes a backbone edge bridge.
 3. The methodof claim 1, wherein the mobility tunnel is established between awireless switching plane component and the edge switch.
 4. The method ofclaim 1, further comprising: determining that a client device is roamingto a different access point; and dynamically binding the mobility VLANnetwork to a service instance identifier (ISID) at a wireless switchingplane component associated with the different access point.
 5. A systemcomprising one or more processors configured to perform operationsincluding: terminating, using one or more processors, an access tunnelat an edge switch of a fabric-enabled network, wherein the fabricenabled network includes a shortest path bridging mac-in-macencapsulation (SPBm) network; establishing, using the one or moreprocessors, a mobility tunnel with the edge switch; interconnecting,using the one or more processors, the mobility tunnel on the edge switchwith another mobility tunnel associated with a wireless switching planecomponent; mapping, using the one or more processors, a mobility VLANnetwork to a service instance identifier (ISID) of the SPBm network soas to associate the ISID with the mobility VLAN network; and exchanging,using the one or more processors, traffic from the mobility tunnelassociated with the edge switch with traffic from the other mobilitytunnel associated with the wireless switching plane component accordingto an ISID value within the traffic.
 6. The system of claim 5, whereinthe edge switch includes a backbone edge bridge.
 7. The system of claim5, wherein the other mobility tunnel is established between a wirelessswitching plane component and a non-fabric enabled network.
 8. Thesystem of claim 5, further comprising: determining that a client deviceis roaming to a different access point; and dynamically binding themobility VLAN network to a service instance identifier (ISID) at awireless switching plane component associated with the different accesspoint.
 9. A nontransitory computer readable medium having stored thereonsoftware instructions that, when executed by a processor, cause theprocessor to perform operations including: terminating, using one ormore processors, an access tunnel at an edge switch of a fabric-enablednetwork, wherein the fabric enabled network includes a shortest pathbridging mac-in-mac encapsulation (SPBm) network; establishing, usingthe one or more processors, a mobility tunnel with the edge switch;mapping, using the one or more processors, a mobility VLAN network to aservice instance identifier (ISID) of the SPBm network so as toassociate the ISID with the mobility VLAN network; and forwarding, usingthe one or more processors, traffic for the mobility VLAN network fromthe edge switch to another edge switch across the fabric enablednetwork, wherein the traffic includes the ISID associated with themobility VLAN.
 10. The nontransitory computer readable medium of claim9, wherein the edge switch includes a backbone edge bridge.
 11. Thenontransitory computer readable medium of claim 9, wherein the mobilitytunnel is established between a wireless switching plane component andthe edge switch.
 12. The nontransitory computer readable medium of claim9, further comprising: determining that a client device is roaming to adifferent access point; and dynamically binding the mobility VLANnetwork to a service instance identifier (ISID) at a wireless switchingplane component associated with the different access point.